Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Tree preservation zone

There is a problem

  • tree-preservation-order column is missing values

entity: 19137685

reference
8
name
tree-preservation-order

tree-preservation-order missing

tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.192140 51.498380,-0.192210 51.498480,-0.192240 51.498510,-0.192220 51.498540,-0.192230 51.498560,-0.192390 51.498760,-0.192390 51.498770,-0.192460 51.498850,-0.192280 51.498900,-0.192560 51.499360,-0.192790 51.499760,-0.192920 51.500030,-0.193430 51.500900,-0.193560 51.500860,-0.193820 51.500760,-0.194070 51.500680,-0.194410 51.500550,-0.197820 51.499340,-0.197880 51.499310,-0.197790 51.499200,-0.197690 51.499060,-0.197770 51.499040,-0.197390 51.498450,-0.197680 51.498400,-0.197980 51.498340,-0.197980 51.498330,-0.198160 51.498300,-0.198430 51.498710,-0.198620 51.499020,-0.199650 51.498770,-0.200380 51.498610,-0.201200 51.498330,-0.202320 51.497920,-0.202440 51.497870,-0.203940 51.497350,-0.204550 51.497130,-0.204110 51.496700,-0.203820 51.496560,-0.202730 51.495590,-0.202910 51.495520,-0.203050 51.495440,-0.203390 51.495280,-0.203050 51.494990,-0.202930 51.495060,-0.202780 51.495120,-0.202690 51.495170,-0.202370 51.494900,-0.202250 51.494910,-0.202200 51.494870,-0.202170 51.494860,-0.202000 51.494820,-0.201670 51.494760,-0.201540 51.494720,-0.201520 51.494720,-0.201530 51.494690,-0.201480 51.494640,-0.201470 51.494610,-0.201480 51.494550,-0.201510 51.494510,-0.201490 51.494490,-0.201660 51.494430,-0.201630 51.494390,-0.201890 51.494310,-0.201850 51.494280,-0.201890 51.494260,-0.201900 51.494270,-0.201910 51.494260,-0.201930 51.494280,-0.201960 51.494270,-0.201960 51.494260,-0.201980 51.494250,-0.201990 51.494270,-0.202020 51.494260,-0.201870 51.494110,-0.199910 51.494780,-0.199670 51.494500,-0.199680 51.494490,-0.199760 51.494460,-0.199730 51.494430,-0.199740 51.494420,-0.199730 51.494400,-0.199700 51.494410,-0.199650 51.494350,-0.199660 51.494350,-0.199650 51.494330,-0.199590 51.494360,-0.199560 51.494350,-0.199460 51.494240,-0.199470 51.494220,-0.199560 51.494190,-0.199520 51.494140,-0.199510 51.494150,-0.199430 51.494080,-0.199520 51.494050,-0.199350 51.493850,-0.199280 51.493780,-0.199110 51.493830,-0.199020 51.493870,-0.198980 51.493880,-0.199290 51.494230,-0.199170 51.494270,-0.199150 51.494270,-0.198740 51.494410,-0.198530 51.494180,-0.198510 51.494140,-0.198480 51.494120,-0.198370 51.494150,-0.197990 51.494290,-0.197910 51.494310,-0.197600 51.494420,-0.197580 51.494420,-0.197130 51.494580,-0.197220 51.494670,-0.197370 51.494840,-0.196150 51.495270,-0.196200 51.495330,-0.196350 51.495480,-0.196730 51.495830,-0.196640 51.495870,-0.196020 51.496100,-0.195880 51.495950,-0.195740 51.495820,-0.195720 51.495820,-0.195720 51.495800,-0.195820 51.495760,-0.195610 51.495550,-0.195540 51.495490,-0.195680 51.495810,-0.195340 51.495940,-0.195320 51.495920,-0.195290 51.495920,-0.195280 51.495890,-0.195030 51.495940,-0.194760 51.495980,-0.194750 51.495990,-0.194590 51.496020,-0.194480 51.496030,-0.194470 51.496040,-0.194430 51.496040,-0.194300 51.496070,-0.194200 51.496080,-0.194130 51.496100,-0.194030 51.496110,-0.194010 51.496120,-0.193840 51.496150,-0.193840 51.496140,-0.193770 51.496150,-0.193690 51.496150,-0.193690 51.496160,-0.193210 51.496180,-0.193130 51.496190,-0.193010 51.496190,-0.192940 51.496200,-0.192790 51.496200,-0.192800 51.496360,-0.192810 51.496380,-0.192810 51.496440,-0.192820 51.496480,-0.192650 51.496480,-0.192600 51.496490,-0.192320 51.496490,-0.192320 51.496720,-0.192340 51.497370,-0.192470 51.497620,-0.191770 51.497840,-0.192140 51.498380)))
point
POINT (-0.197668 51.497227)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL